-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: shadow dom bugs #1049
Fix: shadow dom bugs #1049
Conversation
When moving an element containing shadow dom When adding an element to shadow dom before its attached to the dom
…nto shadow-dom-bugs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I apologise for my late review. It took me a long time to understand the logic of ProcessedNodeManager as well as the new appended shadow dom tests. They are actually essential and delicate. There are two points which I think can be improved.
## Summary Bring in rrweb-io/rrweb#1049 to fix shadow dom recording bugs. Related PRs: * highlight/docs#32 * highlight/highlight-javascript#9 * highlight/rrweb#100 ## How did you test this change? Local deploy on /1/buttons shadow dom example. ## Are there any deployment considerations? New version 5.2.2.
@Mark-Fenng @Juice10 |
@bhavitsharma could you create a separate issue for this including a test case and/or example recording where this is going wrong? Looking at the requestAnimationFrame code, it shouldn’t impact any scroll or click events. |
Fixes a number of shadow dom bugs included bugs related to moving shadow dom parents, and attaching elements to a shadow dom that hasn't been added to a page yet.